-
Notifications
You must be signed in to change notification settings - Fork 13
Update generator throttler to support block-based strategy #1675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
c4199fc to
6ed7dca
Compare
a5dc28f to
10ba2f9
Compare
10ba2f9 to
d724a4c
Compare
74c2f05 to
9ae8ce6
Compare
3c1df18 to
01c4cd3
Compare
a636e4c to
661d654
Compare
af8d207 to
cf2d888
Compare
e1d8abc to
e73bb21
Compare
cf2d888 to
e564637
Compare
e73bb21 to
57bce08
Compare
e564637 to
a1be97c
Compare
57bce08 to
a47d241
Compare
a47d241 to
88ac56e
Compare
a1be97c to
47e1784
Compare
88ac56e to
1692f26
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|

What does this PR do?
Enables configuring byte-based throttlers in generators to be based per block (e.g. 10 blocks per second instead of 100 MB/s).
Impl. details:
Motivation
When using payload generators where blocks are intentionally not the same size/close to maximum bytes, it can be helpful to reason about throughput per block. This allows us to do things like:
to simulate generating logs at 5x standard playback speed.
Related issues
A follow up pr (#1683) adds some flushing logic to BufWriter based generators that enables more regular flushing. A separate PR will introduce a new payload format to utilize block-based throttling.